Device, system and method of wireless communication

ABSTRACT

Some demonstrative embodiments include devices, systems and/or methods of wireless communication. For example, a wireless communication unit may include a Multi Media-Access-Control (MAC) Address Station-Management-Entity (MM-SME) managing a plurality of MAC entities having a respective plurality of MAC addresses. The wireless communication unit may transmit a frame including a Multi-MAC-Addresses-Element (MMAE), which includes two or more MAC addresses of the plurality of MAC addresses and a control field defining at least one common communication attribute to be applied to the two or more MAC addresses.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent application No. 61/380,379, entitled “Method Systemand Apparatus for Communication At Wireless Link”, filed Sep. 7, 2010,the entire disclosure of which is incorporated herein by reference.

BACKGROUND

A first wireless communication device and a second wirelesscommunication device may establish a wireless communication link.

The first and/or second wireless communication devices may include, forexample, a mmWave station (STA) (“DBand STA”) having a radio transmitteroperating on a channel that is within a directional band (“DBand”). TheDBand may include any suitable frequency band, e.g., having a channelstarting frequency above 50 GHz, in which a STA is allowed to operate.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a Multi-MAC-Addresses-Element(MMAE) frame, in accordance with some demonstrative embodiments.

FIG. 3 is a schematic illustration of a MMAE control field, inaccordance with some demonstrative embodiments.

FIG. 4 is a schematic illustration of a method of wirelesscommunication, in accordance with some demonstrative embodiments.

FIG. 5 is a schematic illustration of an article of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality” as used herein include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

Some embodiments may be used in conjunction with various devices andsystems, for example, a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, aPersonal Digital Assistant (PDA) device, a handheld PDA device, anon-board device, an off-board device, a hybrid device, a vehiculardevice, a non-vehicular device, a mobile or portable device, a consumerdevice, a non-mobile or non-portable device, a wireless communicationstation, a wireless communication device, a wireless Access Point (AP),a wired or wireless router, a wired or wireless modem, a video device,an audio device, an audio-video (A/V) device, a wired or wirelessnetwork, a wireless area network, a Wireless Video Area Network (WVAN),a Local Area Network (LAN), a Wireless LAN (WLAN), a Personal AreaNetwork (PAN), a Wireless PAN (WPAN), devices and/or networks operatingin accordance with existing Wireless-Gigabit-Alliance (WGA)specifications (Wireless Gigabit Alliance, Inc WiGig MAC and PHYSpecification Version 1.0, April 2010, Final specification) and/orfuture versions and/or derivatives thereof, devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2007, IEEE Standard for Information Technology—Telecommunicationsand information exchange between systems—Local and metropolitan areanetworks—Specific requirements, Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications; IEEE802.11n-2009, IEEE Standard for InformationTechnology—Telecommunications and information exchange betweensystems—Local and metropolitan area networks—Specific requirements, Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)specifications, Amendment 5: Enhancements for Higher Throughput;IEEE802.11 task group ac (TGac) (“IEEE802.11-09/0308r12—TGac ChannelModel Addendum Document”), IEEE 802.11 task group ad (TGad)) (IEEEP802.11ad/D1.0 Draft Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 5: Enhancements for Very High Throughput in the60 GHz Band), and/or future versions and/or derivatives thereof, devicesand/or networks operating in accordance with existing IEEE 802.16standards (IEEE-Std 802.16, 2009 Edition, Air Interface for FixedBroadband Wireless Access Systems; IEEE-Std 802.16e, 2005 Edition,Physical and Medium Access Control Layers for Combined Fixed and MobileOperation in Licensed Bands; amendment to IEEE Std 802.16-2009,developed by Task Group m) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWireless-WirelessHD™ specifications and/or future versions and/orderivatives thereof, units and/or devices which are part of the abovenetworks, one way and/or two-way radio communication systems, cellularradio-telephone communication systems, a cellular telephone, a wirelesstelephone, a Personal Communication Systems (PCS) device, a PDA devicewhich incorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device (e.g., BlackBerry, PalmTreo), a Wireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Time-Division Multiplexing (TDM), Time-DivisionMultiple Access (TDMA), Extended TDMA (E-TDMA), General Packet RadioService (GPRS), extended GPRS, Code-Division Multiple Access (CDMA),Wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrierCDMA, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT),Bluetooth®, Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™,Ultra-Wideband (UWB), Global System for Mobile communication (GSM), 2G,2.5G, 3G, 3.5G, Enhanced Data rates for GSM Evolution (EDGE), or thelike. Other embodiments may be used in various other devices, systemsand/or networks.

The term “wireless device” as used herein includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

Some demonstrative embodiments may be used in conjunction with suitablelimited-range or short-range wireless communication networks, forexample, a wireless area network, a “piconet”, a WPAN, a WVAN and thelike. Other embodiments may be used in conjunction with any othersuitable wireless communication network.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmwave)frequency band), e.g., a frequency band within the frequency band ofbetween 30 Ghz and 300 GHZ, a WLAN frequency band, a WPAN frequencyband, a frequency band according to the WGA specification, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include an antenna covered by a quasi-omniantenna pattern. For example, the antenna may include at least one of aphased array antenna, a single element antenna, a set of switched beamantennas, and the like.

The phrase “quasi-omni antenna pattern”, as used herein, may include anoperating mode with a widest practical beamwidth attainable for aparticular antenna.

The term “station” (STA), as used herein, may include any logical entitythat is a singly addressable instance of a medium access control (MAC)and a physical layer (PHY) interface to a wireless medium (WM).

The phrase “access point” (AP), as used herein, may include an entitythat contains one station (STA) and provides access to distributionservices, via the WM for associated STAs.

The term “association”, as used herein may relate to a service used toestablish access point/station (AP/STA) mapping and enable STAinvocation of distribution system services (DSSs).

The term “authentication”, as used herein may relate to a service usedto establish the identity of one station (STA) as a member of the set ofSTAs authorized to associate with another STA.

The term “beamforming”, as used herein, may relate to a spatialfiltering mechanism, which may be used at a transmitter to improve thereceived signal power or signal-to-noise ratio (SNR) at an intendedreceiver.

The phrase “non-access-point (non-AP) station (STA)”, as used herein,may relate to a STA that is not contained within an AP.

The phrase “service period” (SP), as used herein, may relate to acontiguous time during which one or more downlink individually addressedframes are transmitted to a quality of service (QoS) station (STA)and/or one or more transmission opportunities (TXOPs) are granted to thesame STA.

The phrase “directional band” (DBand), as used herein, may relate to afrequency band wherein the Channel starting frequency is above 45 GHz.

The phrase “Ultra Band (UB)” may relate to the frequency band of 57-66GHz.

The phrase “mmWave STA (STA)” may relate to a STA having a radiotransmitter which is operating on a channel that is within the UB.

The phrase “multiple MAC addresses Station Management Entity (SME)”(MM-SME), as used herein, may relate to a component of stationmanagement that coordinates management of multiple cooperating STAs. ASTA coordinated and/or managed by a MM-SME is also referred to as a“MM-SME coordinated STA”. A MAC entity coordinated and/or managed by aMM-SME is also referred to as a “MM-SME coordinated MAC entity”.

The phrase “personal basic service set” (PBSS), as used herein, mayrelate to a basic service set (BSS) that forms a self-contained network.For example, the PBSS may operate in the DBand, and may include one PBSScontrol point (PCP).

The phrase “PBSS control point” (PCP), as used herein, may include anentity that contains one station (STA) and coordinates access to the WMby STAs that are members of a PBSS.

The phrase “non-PCP station (STA)”, as used herein, may relate to a STAthat is not also a PCP.

The phrase “non-PCP/non-AP station (STA)”, as used herein, may relate toa STA that is not a PCP and that is not an AP.

The phrase “PCP/AP”, as used herein, may relate to a STA that is a PCPor an AP.

The phrase “multiple MAC addresses link (MMAL)” may relate to a linkbetween two STAs, wherein one of the STAs is coordinated by an MM-SMEthat delivered a MMAE to the other peer STA.

The phrase “multiple MAC addresses link cluster” may relate to allmultiple MAC addresses links between a pair of STAs.

The phrase “peer to peer traffic specification” (PTP TSPEC) may relateto Quality of Service (QoS) characteristics of a data flow betweennon-AP QoS stations.

Reference is now made to FIG. 1, which schematically illustrates a blockdiagram of a system 100 in accordance with some demonstrativeembodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude a wireless communication network including one or more wirelesscommunication devices, e.g., wireless communication devices 102 and/or130, capable of communicating content, data, information and/or signalsover one or more suitable wireless communication links, for example, aradio channel, an IR channel, a RF channel, a Wireless Fidelity (WiFi)channel, and the like. One or more elements of system 100 may optionallybe capable of communicating over any suitable wired communication links.

In some demonstrative embodiments, wireless communication devices 102and/or 130 may include, for example a PC, a desktop computer, a mobilecomputer, a laptop computer, a notebook computer, a tablet computer, aserver computer, a handheld computer, a handheld device, a PDA device, ahandheld PDA device, an on-board device, an off-board device, a hybriddevice (e.g., combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a non-mobile or non-portabledevice, a cellular telephone, a PCS device, a PDA device whichincorporates a wireless communication device, a mobile or portable GPSdevice, a DVB device, a relatively small computing device, a non-desktopcomputer, a “Carry Small Live Large” (CSLL) device, an Ultra MobileDevice (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device (MID),an “Origami” device or computing device, a device that supportsDynamically Composable Computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-raydisc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, aHigh Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, aPersonal Video Recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a Personal Media Player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a Digital Still camera (DSC), a media player, a Smartphone, atelevision, a music player, or the like.

In some demonstrative embodiments, wireless communication devices 102and/or 130 may include wireless communication units 104 and/or 132,respectively, to perform wireless communication with wirelesscommunication devices 102 and/or 130, respectively, and/or with one ormore other wireless communication devices, e.g., as described below.

Wireless communication devices 102 and/or 130 may also include, forexample, one or more of a processor 114, an input unit 106, an outputunit 108, a memory unit 110, and a storage unit 112, Wirelesscommunication devices 102 and/or 130 may optionally include othersuitable hardware components and/or software components. In somedemonstrative embodiments, some or all of the components of one or moreof wireless communication devices 102 and/or 130 may be enclosed in acommon housing or packaging, and may be interconnected or operablyassociated using one or more wired or wireless links. In otherembodiments, components of one or more of wireless communication devices102 and/or 130 may be distributed among multiple or separate devices.

Processor 114 includes, for example, a Central Processing Unit (CPU), aDigital Signal Processor (DSP), one or more processor cores, asingle-core processor, a dual-core processor, a multiple-core processor,a microprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 114 executes instructions,for example, of an Operating System (OS) of wireless communicationdevices 102 and/or 130 and/or of one or more suitable applications.

Input unit 106 includes, for example, a keyboard, a keypad, a mouse, atouch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 108 includes, for example,a monitor, a screen, a flat panel display, a Cathode Ray Tube (CRT)display unit, a Liquid Crystal Display (LCD) display unit, a plasmadisplay unit, one or more audio speakers or earphones, or other suitableoutput devices.

Memory unit 110 includes, for example, a Random Access Memory (RAM), aRead Only Memory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM(SD-RAM), a flash memory, a volatile memory, a non-volatile memory, acache memory, a buffer, a short term memory unit, a long term memoryunit, or other suitable memory units. Storage unit 112 includes, forexample, a hard disk drive, a floppy disk drive, a Compact Disk (CD)drive, a CD-ROM drive, a DVD drive, or other suitable removable ornon-removable storage units. Memory unit 110 and/or storage unit 112,for example, may store data processed by wireless communication devices102 and/or 130.

In some demonstrative embodiments, wireless communication units 104 and132 may include, or may be associated with, one or more antennas 105 and133, respectively. Antennas 105 and/or 133 may include any type ofantennas suitable for transmitting and/or receiving wirelesscommunication signals, blocks, frames, transmission streams, packets,messages and/or data. For example, antennas 105 and/or 133 may includeany suitable configuration, structure and/or arrangement of one or moreantenna elements, components, units, assemblies and/or arrays. Antennas105 and/or 133 may include an antenna covered by a quasi-omni antennapattern. For example, antennas 105 and/or 133 may include at least oneof a phased array antenna, a single element antenna, a set of switchedbeam antennas, and the like. In some embodiments, antennas 105 and/or133 may implement transmit and receive functionalities using separatetransmit and receive antenna elements. In some embodiments, antennas 105and/or 133 may implement transmit and receive functionalities usingcommon and/or integrated transmit/receive elements.

In some demonstrative embodiments, wireless communication units 104and/or 132 include, for example, one or more wireless transmitters,receivers and/or transceivers able to send and/or receive wirelesscommunication signals, RF signals, frames, blocks, transmission streams,packets, messages, data items, and/or data. For example, wirelesscommunication units 104 and/or 132 may include or may be implemented aspart of a wireless Network Interface Card (NIC), and the like.

In some demonstrative embodiments, wireless communication devices 102and 130 may establish a wireless communication link. The link mayinclude an uplink and/or a downlink. The downlink may include, forexample, a unidirectional link from an AP to one or more non-AP stations(STAs) or a unidirectional link from a non-AP Destination STA to anon-AP Source STA. The uplink may include, for example, a unidirectionallink from a non-AP STA to an AP or a unidirectional link from a non-APSource STA to a non-AP Destination STA.

In some demonstrative embodiments, wireless communication devices 102and/or 130 may perform the functionality of mmWave stations (“DBandSTA”).

In some demonstrative embodiments, wireless communication unit 104 mayinclude a Multi Media-Access-Control (MAC) Station-Management-Entity(MM-SME) 146 managing a plurality of stations (STAs) having a respectiveplurality of MAC addresses. For example, MM-SME 146 may manage three MACentities of three respective STAs, e.g., MAC entities 140, 142 and/or144, having three respective MAC addresses.

In some demonstrative embodiments, wireless communication unit 104 mayinclude a common physical Layer (PHY) shared the plurality of MACentities. For example, MAC entity 140 may include a MAC sub-layer 153having a first MAC address, MAC entity 142 may include a MAC sub-layer154 having a second MAC address, and MAC entity 144 may include a MACsub-layer 155 having a third MAC address. MAC sub-layers 153, 154 and155 may share, for example, a common PHY layer, e.g., including a commonPhysical Layer Convergence Protocol (PLCP) sub-layer 152 and a commonPhysical Medium Dependent (PMD) sub-layer 150.

In some demonstrative embodiments, SME 146 may include an MM-SME tocoordinate with SMEs in other STAs and/or support multiple MACaddresses. The MM-SME may coordinate the management of multiple MACentities having MAC sublayers, e.g., MAC sub-layers 153, 154 and 155.For example, each of MAC sub-layers 153, 154 and 155 may have a separateMAC Service Access Point (SAP) and a MAC sub-layer management entity(MLME) SAP. Each MAC entity may be identified by a separate MAC address.

In some demonstrative embodiments, MM-SME 146 may manage the pluralityof STAs using a respective plurality of security keys. For example,MM-SME 146 may control the MAC SAPs of MAC entities 140, 142 and/or 144using separate and/or independent Robust Security Network Association(RSNA) key management entities 147, 148 and 149, respectively.

In some demonstrative embodiments, MAC sub-layers 153, 154 and/or 155may utilize a back-off mechanism for accessing the shared PHY layer, forexample, in order to avoid collision of transmission attempts of MACsub-layers 153, 154 and/or 155.

In some demonstrative embodiments, MM-SME 146 may be configured tocontrol the power management mode, DBand antenna configuration and/orother parameters and/or states of MAC entities 140, 142 and/or 144, toeliminate unnecessary duplication of functions.

In some demonstrative embodiments, MM-SME 146 may signal to a peer STA achange in the power management mode of the STAs coordinated by MM-SME146 via any one of MAC entities 140, 142 and 144, e.g., as describedbelow.

In some demonstrative embodiments, a beamforming link establishedbetween STAs may be used by all MAC sub-layers 153, 154 and 155coordinated by the same MM-SME 146, e.g., as described in detail below.

In some demonstrative embodiments, wireless communication unit 104 maytransmit, e.g., to device 130, a frame including aMulti-MAC-Addresses-Element (MMAE), which includes two or more MACaddresses of the plurality of MAC addresses managed by MM-SME 146, and acontrol field defining at least one common communication attribute to beapplied to the two or more MAC addresses, e.g., as described in detailbelow. In one example, wireless communication unit 104 may transmit aMMAE including the MAC addresses of MAC entities 140 and 144 and acontrol field defining at least one common communication attribute to beapplied to MAC entities 140 and 144. In another example, wirelesscommunication unit 104 may transmit a MMAE including the MAC addressesof MAC entities 140, 142 and 144 and a control field defining at leastone common communication attribute to be applied to MAC entities 140,142 and 144

In some demonstrative embodiments, wireless communication unit 104 maytransmit the MMAE as part of a management action frame, e.g., to device130. For example, wireless communication unit 104 may transmit the MMAEas part of a probe request frame, a probe response frame, an associationrequest frame, an association response frame, a Traffic StreamEstablishment (TSE) frame, an announce frame, an information requestframe, or an information response frame.

In some demonstrative embodiments, wireless communication unit 104 maytransmit the MMAE as part of any frame that advertises MM-SMEcapabilities of SME 146, for example, as part of probe and/orinformation request and/or response frames, as part of one or moreframes that establish communication agreements, for example,association, Add-Traffic-Specification (ADDTS) and/orBlock-Acknowledgment (BA) requests and/or responses, and the like.

In some demonstrative embodiments, the control field of the MMAE mayinclude a Single-Association-Identifier (AID) bit indicating whether asingle AID is to be used for commonly identifying the two or more MACaddresses included in the MMAE, e.g., as described in detail below.

In some demonstrative embodiments, the control field of the MMAE mayinclude a MMAE owner value identifying an owner MAC entity of the MMAE.

For example, the MMAE owner value may have a first value representing noowner, a second value representing a non-Access-Point (AP) ornon-Personal-Basic-Service-Set-Control-Point (PCP), a third valuerepresenting a PCP, or a fourth value representing an AP, e.g., asdescribed in detail below.

In some demonstrative embodiments, the control field of the MMAE mayinclude a power-mode bit indicating a common power state scheme to beapplied to two or more MAC entities having the two or more MACaddresses.

For example, the power-mode bit may have either a first value indicatingthat when a MAC entity of the two or more MAC entity moves from an awakestate to a doze state all other MAC entities of the two or more MACentities move to the doze state and that the MAC entity moves from thedoze state to the awake state only when all the other MAC entities moveto the awake state, or a second value indicating that when the MACentity moves from thee doze state to the awake state all the other MACentities move to the awake state and that the MAC entity moves from theawake state to the doze state only when all the other MAC entities moveto the doze state, e.g., as described in detail below.

In some demonstrative embodiments, the control field of the MMAE mayinclude a beamlink cluster bit indicating whether or not a commonbeamformed link is to be utilized for communication by two or more MACentities having the two or more MAC addresses, e.g., as described indetail below.

In some demonstrative embodiments, wireless communication unit 104 mayutilize the MMAE to establish a Multiple-MAC-Address-Link (MMAL) clusterwith device 130. The MMAL cluster may include a plurality of linksbetween the two or more MAC addresses included in the MMAE and one ormore MAC addresses of device 130, e.g., as described in detail below.

For example, the MMAE may include the MAC addresses of MAC entities 140and 144, and the MMAL cluster may include links between MAC entities 140and 144 and one or more MAC entities of device 130.

In one example, device 130 may include a plurality of MAC entities. Forexample, the MMAL cluster may include links between MAC entities 140 and144 and first, second, and third MAC entities of device 130. Accordingto this example, the MMAL cluster may include six links, e.g., a linkbetween MAC entity 140 and the first MAC entity of device 130, a linkbetween MAC entity 140 and the second MAC entity of device 130, a linkbetween MAC entity 140 and the third MAC entity of device 130, a linkbetween MAC entity 144 and the first MAC entity of device 130, a linkbetween MAC entity 144 and the second MAC entity of device 130, and alink between MAC entity 144 and the third MAC entity of device 130.

In another example, device 130 may include one MAC entity. For example,the MMAL cluster may include links between MAC entities 140 and 144 andthe MAC entity of device 130. According to this example, the MMALcluster may include two links, e.g., a link between MAC entity 140 andthe MAC entity of device 130, and a link between MAC entity 144 and theMAC entity of device 130.

In some demonstrative embodiments, wireless communication unit 104 maytransmit the MMAE as part of an association request frame to a PCP or anAP (PCP/AP), and the MMAE may include a Transmit Address (TA) field usedfor transmission of the association request frame, e.g., as describedbelow.

In some demonstrative embodiments, wireless communication unit 104 mayreceive from the PCP/AP an association response frame including theMMAE, e.g., as described below.

In some demonstrative embodiments, the association response frame mayinclude a Receive Address (RA) field equal to the TA field, e.g., asdescribed below.

Reference is made to FIG. 2, which schematically illustrates a MMAE 200,in accordance with some demonstrative embodiments.

In some embodiments, MMAE 200 may be transmitted as part of a suitableframe between first and second wireless communication devices, e.g.,DBand STAs, for example, wireless communication devices 102 and/or 130(FIG. 1).

In some demonstrative embodiments, MMAE 200 may be transmitted by a MACentity of one or more MAC entities of a wireless communication device.For example, MMAE 200 may be transmitted by a MAC entity of MAC entities140, 142 and 144 (FIG. 1).

In some demonstrative embodiments, MMAE 200 may include an elementidentification (ID) field 202, a length field 204, a MMAE control field206, a STA MAC field 208, and an interface address field 210, e.g., asdescribed below.

In some demonstrative embodiments, element ID field 202 may have apredefined value indicating that MMAE 200 is related to multiple MACaddresses. For example, element ID field 202 may have a length of 1octet.

In some demonstrative embodiments, length field 204 may include a valueindicating a length of MMAE 200 or the length of one or more fields ofMMAE 200, e.g., subsequent to length field 204. For example, lengthfield 204 may have a length of 1 octet.

In some demonstrative embodiments, MMAE 200 may include one or morefields to identify one or more MAC addresses of one more MAC entities ofthe MAC entities of the wireless communication device. For example,fields 208 and/or 210 may include one or more MAC addresses of one ormore of the MAC entities of the wireless communication device, e.g., asdescribed below.

In some demonstrative embodiments, STA MAC field 208 may include a MACaddress of the MAC entity, from which the MMAE is transmitted. Forexample, STA MAC field 208 may include the MAC address of MAC entity 140(FIG. 1), e.g., if MMAE 200 is transmitted by MAC entity 140 (FIG. 1).For example, STA MAC field 208 may have a length of six octets.

In some demonstrative embodiments, field 210 may optionally be includedas part of MMAE 200, for example, to identify one or more additional MACaddresses of one or more MAC entities other that the MAC entity, fromwhich the MMAE is transmitted. For example, field 210 may include one ormore MAC addresses of one or more of MAC entities 142 and 144 (FIG. 1),e.g., if MMAE 200 is transmitted by MAC entity 140 (FIG. 1). Forexample, field 210 may have a length of 6*n octets, wherein n is aninteger variable denoting the number of the additional MAC addresses.

In some demonstrative embodiments, control field 206 may include one ormore values defining at least one common communication attribute to beapplied to the MAC addresses of fields 208 and 210, e.g., as describedin detail below.

Reference is made to FIG. 3, which schematically illustrates a MMAEcontrol field 300, in accordance with some demonstrative embodiments.

In some embodiments, MMAE control field 300 may be transmitted as partof a MMAE, e.g., MMAE 200 (FIG. 2).

In some demonstrative embodiments, MMAE control field 300 may include aMMAE owner field 302, a single AID filed 304, a MM-SME power mode field306, a beamlink cluster field 308, and a reserved field 310, asdescribed in detail below.

In some demonstrative embodiments, MMAE owner field 302 may include aMMAE owner value identifying an owner MAC entity of the MMAE. Forexample, MMAE owner field 302 may include a first value representing noowner, a second value representing a non-Access-Point (AP) ornon-Personal-Basic-Service-Set-Control-Point (PCP), a third valuerepresenting a PCP, or a fourth value representing an AP, e.g., asdescribed in detail below.

In one example, MMAE owner field 302 may have include two bits, denotedB0 and B1, which may be encoded, for example, as follows:

TABLE 1 MMAE owner B0 B1 Meaning 0 0 No owner 1 0 Non-AP, Non-PCP MMAE 01 PCP MMAE 1 1 AP MMAE

In some demonstrative embodiments, single AID field 304 may indicatewhether a single AID is to be used for commonly identifying the MACaddresses identified by the MMAE, e.g., the MAC addresses of fields 208and 210 (FIG. 2).

For example, single AID field 304 may have include one bit, denoted B3,which may be encoded, for example, as follows:

TABLE 2 MMAE Single MMAE MMAE sent owner AID sent from to B0 B1 B3Meaning Non- PCP/AP 1 0 1 Request to allocate single PCP, non- AID forMAC addresses AP STA included in the MMAE Non- PCP/AP 1 0 0 Don'tallocate single PCP, non- AID for MAC addresses AP STA included in theMMAE PCP/AP Non- 1 0 1 Single AID is allocated STA PCP, non-AP for allMAC STA addresses in the MMAE PCP/AP Non- 1 0 0 Single AID is not STAPCP, non-AP allocated for all MAC STA addresses in the MMAE Non- Non- 10 1 Single AID is allocated PCP, non- PCP, non-AP for all MAC AP STA STAaddresses in the MMAE Non- Non- 1 0 0 Single AID is not PCP, non- PCP,non-AP allocated for all MAC AP STA STA addresses in the MMAE PCP/APNon- 0 1 1 Single AID is allocated STA PCP, non-AP for all MAC STAaddresses in the non-PCP, non-AP STA MMAE PCP/AP Non- 0 1 0 Single AIDis not STA PCP, non-AP allocated for all MAC STA addresses in thenon-PCP, non-AP STA MMAE

As shown in Table 2, for example, the values of fields 302 and 304 maybe determined, for example, based on whether or not the MAC entitytransmitting the MMAE is an AP/PCP MAC entity and/or based on whether ornot as single AID is to be allocated to all MAC addresses identified bythe MMAE. For example, per the two last rows of Table 2, a PCP/AP MACentity may send a response to a request frame including an MMAE from anon-PCP/AP MAC entity to acknowledge the allocation of a single AID toall MAC addresses in the MMAE from the non-PCP/AP MAC entity.

In some demonstrative embodiments, field 306 may include a power-modebit indicating a common power state scheme to be applied to two or moreMAC entities having two or more MAC addresses identified by the MMAE,e.g., the MAC addresses of fields 208 and 210 (FIG. 2).

For example, the power-mode bit may have either a first value, e.g., “1”or a second value, e.g., “0”. The first value, e.g., “1”, may indicatethat when a MAC entity, e.g., MAC entity 140 (FIG. 1), advertised in theMMAE, e.g., MMAE 200 (FIG. 2), sent by the MAC entity, e.g., MAC entity140 (FIG. 1), coordinated by an MM-SME, e.g., MM-SME 146 (FIG. 1), movesfrom an awake to a doze state, then all other MAC entities, e.g., MACentities 142 and/or 144 (FIG. 1), advertised in the MMAE sent by the MACentity coordinated by the MM-SME, e.g., if the MMAE includes the MACaddresses of MAC entities 142 and/or 144 (FIG. 1), move to the dozestate. The first value, e.g., “1”, may indicate that the MAC entity,e.g., MAC entity 140 (FIG. 1), coordinated by the MM-SME, e.g., MM-SME146 (FIG. 1), moves to the Awake state only when MAC entities advertisedin the MMAE, e.g., MAC entities 142 and/or 144 (FIG. 1), move to theawake state. The first value, e.g., “0”, may indicate that when a MACentity, e.g., MAC entity 140 (FIG. 1), advertised in the MMAE, e.g.,MMAE 200 (FIG. 2), sent by the MAC entity, e.g., MAC entity 140 (FIG.1), moves from the doze to the awake state, then all other MAC entities,e.g., MAC entities 142 and/or 144 (FIG. 1), advertised in the MMAE sentby the MAC entity coordinated by the MM-SME, e.g., if the MMAE includesthe MAC addresses of MAC entities 142 and/or 144 (FIG. 1), move to theawake state. The second value, e.g., “1”, may indicate that the MACentity, e.g., MAC entity 140 (FIG. 1), coordinated by the MM-SME, e.g.,MM-SME 146 (FIG. 1), moves to the doze state only when all MAC entitiesadvertised in the MMAE move to the Doze state.

In some demonstrative embodiments, field 308 may include a beamlinkcluster bit indicating whether or not a common beamformed link is to beutilized for communication by two or more MAC entities having two ormore MAC addresses identified by the MMAE, e.g., the MAC addresses offields 208 and 210 (FIG. 2).

For example, field 308 may include a single bit set to a first value,e.g., “1”, for example, if the MAC entity transmitting the MMAE intendsto maintain the same beamformed link for all links within a MMALcluster. Otherwise, for example, field 308 may be set to a second value,e.g., “0”.

Referring back to FIG. 1, in some demonstrative embodiments, PHYsub-layer 152 may indicate a current transmission state of the PHYlayer, for example, using an indication signal, e.g., denoted,PHY-TxBusy.indication. The signal PHY-TxBusy. indication may include astate parameter having one of two values BUSY or IDLE. The parametervalue is BUSY, for example, if the PHY layer is busy transmitting, e.g.,a PLCP Protocol Data Unit (PPDU), thus not available to respond, e.g.,with a PHY-TXSTART.confirm indication to a PHY-TXSTART.request.Otherwise, the value of the parameter may be IDLE.

The signal PHY-TxBusy.indication may be generated, for example, when thePHY layer issues a PHY-TXSTART.confirm signal to one of the MAC entitiescoordinated by MM-SME 146. The signal PHY-TxBusy.indication may beprovided, for example, to all coordinated MAC entities except, e.g., toa MAC entity that to which the PHY layer responds with thePHY-TXSTART.confirm. The STATE of the signal PHY-TxBusy.indication maybe set to BUSY.

The signal PHY-TxBusy. indication may be generated, for example, withina predefined delay period, TxPLCPDelay, of the occurrence of a change inthe state of a PLCP transmit state machine to a receive (RX) state. TheSTATE of the signal PHY-TxBusy. indication may be set to IDLE.

In some demonstrative embodiments, wireless communication unit 104 mayutilize the MMAE, e.g., MMAE 200 (FIG. 2), to establish a MMAL clusterwith device 130. The MMAL cluster may include a plurality of linksbetween the two or more MAC addresses included in the MMAE and one ormore MAC addresses of device 130, e.g., as described in detail below.

In some demonstrative embodiments, a MAC entity, e.g., MAC entity 140,142 and/or 144, of system 100 may be capable of participating in a MMALcluster if it includes a MMAE, e.g., MMAE 200 (FIG. 2), in a most recenttransmission of, for example, an Association Request, a (Re-)Association Response, a ADDTS Request, a ADDTS Response, a ProbeRequest, a Probe Response, an Information Request or InformationResponse frame, and the like.

20

In some demonstrative embodiments, a MM-SME coordinated MAC entity,e.g., MAC entities 140, 142, and/or 144, may be MMAL cluster capable anda non-MM-SME coordinated MAC entity, e.g., a MAC entity which is notcoordinated by a MM-SME, may be MMAL cluster capable. A MMAL clustercapable MAC entity may include an MMAE, e.g., MMAE 200 (FIG. 2) in atransmitted Association Request frame, Re-association request frame,association response frame, and/or Re-Association Response frame.

In some demonstrative embodiments, all MAC entities coordinated by anMM-SME and indicated within an MMAE may be equivalent, e.g., such thateach MAC entity may be used for MMAL Cluster setup and/or maintenance.

In some demonstrative embodiments, a PCP STA, e.g., a MAC entity of MACentities 140, 142 and 144, which may perform the functionality of a PCPSTA, may transmit a MMAE including a MAC address that is equal to aBasic-Service-Set-ID (BSSID) of the PCP and one or more other MACaddresses, which are not equal to the BSSID. The PCP STA may not use theother MAC addresses, which are not equal to the BSSID, to request and/orrespond to association, re-association, probing and/or schedulingservices provided by the PCP STA.

In some demonstrative embodiments, a non-PCP/non-AP STA, e.g., a MACentity of MAC entities 140, 142 and 144, which may perform thefunctionality of a non-PCP/non-AP STA, may transmit a MMAE, e.g., MMAE200 (FIG. 2) to a PCP/AP. The non-PCP/non-AP STA may not be allowed tosend an ADDTS Request frame to the PCP/AP with a Transmit Address (TA)field equal to a MAC address, which was not included in the deliveredMMAE.

In some demonstrative embodiments, an MA-SME coordinated MAC entity,e.g., a MAC entity of MAC entities 140, 142 and 144, may be associatedwith a PCP/AP that allocates one single AID to all STAs advertised in anMMAE sent by the MM-SME coordinated MAC entity. The AID may be used toidentify an MMAL Cluster. For example, the AID may be provided for oneof the advertised MAC entities of the MA-ME coordinated MAC entity.Accordingly, the same AID may apply to all MAC entities identified bythe MAC addresses in a MMAE having a Single AID field, e.g., field 304(FIG. 3), set to “1”.

In some demonstrative embodiments, a MMAL cluster between a first MM-SMEcoordinated station (“station A”), e.g., MAC entities 140, 142 and/or144, and a second MM-SME coordinated station (“station B”), e.g., one ormore MAC entities of device 130, may be identified using a single commonAID. For example, it may be determined whether or not the MMAL clusteris to be identified using the AID, based on the single AID field, e.g.,field 304 (FIG. 3), of MMAEs exchanged between the STAs.

For example, the MMAL cluster identification may be determined, asfollows:

TABLE 3 Is the Is the Single Single AID AID AID allocated iden-allocated to the tifica- to the MM- MM-SME tion SME coordinated ofcoordinated STA MMAL MMAL cluster configuration STA A? B? clusterNon-PCP/non-AP MM-SME Yes Yes Yes coordinated STA A is associated to PCPMM-SME coordinated STA B Non-PCP/non-AP MM-SME Yes Yes Yes coordinatedSTA A and Non- PCP/non-AP MM-SME coordinated STA B are both associatedto the same BSS Non-PCP/non-AP MM-SME Yes No No coordinated STA A isassociated to a BSS and Non-PCP/non-AP MM- SME coordinated STA B is notassociated to the BSS Non-PCP/non-AP MM-SME Yes N/A Yes coordinated STAA and Non- PCP/non-AP STA B are both associated to the same BSSNon-PCP/non-AP MM-SME Yes N/A Yes coordinated STA A is associated to aBS and one STA of non- PCP/non-AP MM-SME coordinated STA B is associatedto the same BSS

In some demonstrative embodiments, a MMAL cluster may be established bya MM-SME coordinated MAC entity, e.g., MAC entities 140, 142 and/or 144,transmitting to a peer MAC entity a MMAE including a plurality ofadvertised MAC entities, e.g., as described above with reference toFIGS. 2 and/or 3. The peer MAC entity may be an MM-SME coordinated MACentity or a non-MM-SME coordinated MAC entity.

In some demonstrative embodiments, the MMAL cluster may identified, forexample, by advertised MAC addresses of MAC entities of two MM-SMEcoordinated MAC entities; or advertised MAC addresses of the MACentities of an MM-SME coordinated MAC entity and of a non-MM-SMEcoordinated MAC entity.

In some demonstrative embodiments, an MMAL cluster agreement may be setup by exchanging an MMAE between the MAC entities, e.g., as describedbelow.

In some demonstrative embodiments, if a MMAL cluster capable non-MM-SMEcoordinated MAC entity receives an ADDTS Request frame, which includesan MMAE, the SME of the non-MM-SME coordinated MAC entity may includethe received MMAE in a MLME-ADDTS.response primitive used to send anADDTS Response frame, e.g., if the SME accepts the MMAL cluster setup.The SME of the non-MM-SME coordinated MAC entity may set an MMAE ownerfield to “no Ownerll” in the MMAE included in an MLME-ASSOCIATE.requestprimitive and/or a MLME-ADDTS.request primitive, e.g., to establish theMMAL cluster with an MM-SME coordinated STA.

In some demonstrative embodiments, the MAC entities of the MMAL clustermay exchange the MMAE, for example, once per MMAL cluster setup.

In some demonstrative embodiments, an MMAL cluster may be setup betweena non-PCP/non-AP MM-SME coordinated MAC entity and PCP/AP.

For example, association request and response frames may be used toestablish the MMAL cluster between a non-PCP/non-AP MM-SME coordinatedSTA and a PCP/AP. The MMAE control field within the MMAE included in theassociation request and response frames may be asserted, e.g., asdescribed above with reference to FIG. 2. The PCP/AP may include theMMAE received from the non-PCP/non-AP MM-SME coordinated STA in theassociation response frame sent as response, e.g., if the PCP/AP is notan MM-SME coordinated STA. The PCP/AP may include its own MMAE, whichmay include the PCP/AP advertised MAC entities in the associationresponse frame, e.g., if the PCP/AP is an MM-SME coordinated STA. ThePCP/AP may not respond with any MMAE, for example, if the PAP/AP is notMMAL cluster capable. The setup of the MMAL Cluster may fail, forexample, if the association response frame does not contain the MMAE.

In some demonstrative embodiments, an MMAL cluster may be setup betweena non-PCP/non-AP STA with another non-PCP/non-AP STA.

According to these embodiments, if, for example, a non-PCP/non-AP MM-SMEcoordinated STA associated with a PCP/AP has established an AIDidentified MMAL cluster with the PCP/AP, then the non-PCP/non-AP MM-SMEcoordinated STA may not use a MAC address that was not included in theMMAE delivered to the PCP/AP to establish a MMAL cluster with anothernon-PCP/non-AP MM-SME coordinated STA associated with the same PCP/AP.

In some demonstrative embodiments, a MMAL cluster between non-PCP/non-APMM-SME coordinated STAs and/or a MMAL cluster between a non-PCP/non-APMM-SME coordinated STA and a non-PCP/non-AP non-MM-SME coordinated STA,may be set up by exchanging ADDTS Request/Response frames with a PTPTSPEC.

In some demonstrative embodiments, a non-PCP/non-AP MM-SME coordinatedSTA may include an MMAE, which includes, its advertised MAC entities intransmitted ADDTS Request frames. The transmitted MMAE may include anasserted MMAE control field, e.g., as described above with reference toFIGS. 2 and/or 3.

In some demonstrative embodiments, a non-PCP/non-AP STA, which is not anMM-SME coordinated STA, may transmit an ADDTS request frame with a MMAEincluding an owner field, e.g., field 302 (FIG. 3), set to the valuerepresenting “no owner”.

In some demonstrative embodiments, a non-PCP/non-AP MM-SME coordinatedSTA may transmit ADDTS response frames including an MMAE of thenon-PCP/non-AP MM-SME coordinated STA, which includes the advertised MACentities of the non-PCP/non-AP MM-SME coordinated STA. The transmittedMMAE may include an asserted MMAE control field, e.g., as describedabove with reference to FIGS. 2 and/or 3.

In some demonstrative embodiments, the power management mode of MACentities 140, 142 and/or 144 may be commonly managed and/or controlled,e.g., using MMAE 200 (FIG. 2).

In some demonstrative embodiments, a STA that is coordinated by anMM-SME may inform an AP of a change in Power Management mode, forexample, through a successful frame exchange initiated by the STA. Forexample, MAC entities 140, 142 and/or 144 may transmit a MMAE, e.g.,MMAE 200 (FIG. 2) including a MM-SME Power Mode field, e.g., field 306(FIG. 1), set to indicate the Power Management mode that the MACentities coordinated by the MM-SME and advertised in the MMAE may adoptupon successful completion of the frame exchange. The frame may be sent,for example, using any of the MMAL within a MMAL cluster establishedwith the AP, e.g., in order to change the Power Management mode of thecoordinated MAC entity.

For example, if an MA-SME coordinated MAC entity, e.g., MAC entity 140,142 and/or 144, transmits a MMAE, e.g., MMAE 200 (FIG. 2) including aMM-SME Power Mode field, e.g., field 306 (FIG. 1), set to “1”, then allMAC entities, which are advertised in the MMAE, may switch to the Dozestate when the wakeup schedule of any one MAC entity or a successfulframe exchange brings the MAC entity to the Doze state. If, for example,the MA-SME Power Mode field is set to “zero”, then, for example, all MACentities, which are advertised in the MMAE, may switch to the Awakestate when the wakeup schedule of any one MAC entity or a successfulframe exchange brings the MAC entity to the Awake state.

In some demonstrative embodiments, the association, re-associationand/or disassociation, of MAC entities 140, 142 and/or 144 may bemanaged and/or controlled, e.g., using MMAE 200 (FIG. 2).

In some demonstrative embodiments, one or more MAC entities of system100, e.g., MAC entities 140, 142 and/or 144, and/or one or more MACentities of device 130 may utilize a state variable expressing arelative state between a local MAC entity and a remote MAC entity. Forexample, the state variable may have a first value “State 1”representing an initial start state for OBand, e.g., Unauthenticated,unassociated. The state variable may have a second value “State 2”representing an initial start state for DBand, e.g., Authenticated(OBand only), not associated. The state variable may have a third value“State 3” representing, e.g., an Authenticated (OBand only) andassociated (Pending RSN Authentication) state. The state variable mayhave a fourth value “State 4” representing, e.g., an RSNA Established orNot Required (Infrastructure BSS and PBSS only) Authenticated andassociated state.

In some demonstrative embodiments, if an MM-SME coordinated MAC entityreceives an Association Response frame with a result code equal toSUCCESS and including a MMAE, e.g., MMAE 200 (FIG. 2), which includes aSingle AID field, e.g., field 304 (FIG. 3) set to “1”, then the statemay be set to “state 3”, e.g., for each of the MAC entities advertisedwithin the MMAE, for example, for which a dot11RSNAEnabled indication istrue. Progress from “State 3” to “State 4” may occur, for example,independently in each of the MAC entities. The state may be set to“state 4”, e.g., for each of the MAC entities advertised within theMMAE, for example, for which the dot11RSNAEnabled indication is false.

In some demonstrative embodiments, the MM-SME may repeat the associationprocedure for any other MAC entity coordinated by of the MA-SM, if, forexample, the MA-SME coordinated STA in State 3 is assigned an AID foronly a MAC entity identified by an RA field of the Association Responsewith result code equal to SUCCESS.

In some demonstrative embodiments, an MM-SME, e.g., MM-SME 146, of anon-PCP/non-AP STA may include a MMAE, e.g., MMAE 200 (FIG. 2) in anMLME-ASSOCIATE.request primitive. The MM-SME may include in the MMAE theMAC address associated with the MLME SAP instance to which the primitiveis submitted.

In some demonstrative embodiments, if a MM-SME coordinated MAC entityreceives from a PCP/AP an Association Response frame with a status codeof Successful containing an MLME element with the Single AID field setto “1”, then all the MAC entities coordinated by of the MM-SME may beassociated with the PCP/AP, e.g., by setting to State 4, or State 3,e.g., if RSNA Establishment is required.

In some demonstrative embodiments, upon receipt of an AssociationRequest frame from a non-PCP/non-AP STA for which the state is “State2”, “State 3”, or “State 4”, a PCP/AP's MLME may associate with thenon-PCP/non-AP STA.

In some demonstrative embodiments, the PCP/AP may receive from a MLME ofa non-PCP/non-AP MAC entity a MLME-ASSOCIATE.indication primitiveincluding an MMAE parameter, e.g., as part of an association requestframe. The PCP/AP may generate a MLME-ASSOCIATE.response primitivedirected to the MLME of the MAC entity, which may be identified by aPeer STA Address parameter of the MLME-ASSOCIATE.indication primitive.The PCP/AP may allocate a single AID for all the MAC entities includedin the MMAE, if, for example, the Single AID field in the MMAE parameterof the MLME-ASSOCIATE.indication primitive is set to “1”. The PCP/AP mayinclude the MMAE received from the MM-SME coordinated MAC entity in theMLME-ASSOCIATION.response primitive, for example, if the PCP/APallocates the same AID to all MAC entities. The PCP/AP may not allocatea single AID for all MAC entities, for example, if the Single AID fieldof the MMAE is set to “0”.

In some demonstrative embodiments, a MM-SME of a non-PCP/non-AP STA mayinclude a MMAE in an MLME-REASSOCIATE.request primitive. The MM-SME mayinclude in the MMAE the MAC address associated with the MLME SAPinstance to which the primitive is submitted. Upon receipt of theMLME-REASSOCIATE.request primitive, a non-PCP/non-AP MAC entity mayreassociate with a PCP/AP. If a MM-SME coordinated MAC entity receives a

Reassociation Response frame with a status code of Successful containingan MLME element with the Single AID field et to “1”, all the MACentities coordinated by the MM-SME may be reassociated with the PCP/AP,e.g., by setting to “State 4” or “State 3”, e.g., if RSNA Establishmentis required.

In some demonstrative embodiments, MM-SME 146 may commonly perform oneor more disassociation operations with respect to MAC entities, forwhich association was commonly established, e.g., using the Single AIDfield. The disassociaiton operations may include, for example, setting astate of the MAC entities, deleting keys, and the like. For example, anon-PCP/non-AP MAC entity's MLME may disassociate from a PCP/AP, e.g.,upon receipt of an MLME-DISASSOCIATE.request primitive. If the state forthe PCP/AP is State 3 or State 4, the MLME may transmit a Disassociationframe to the PCP/AP. The state for the PCP/AP may be set to State 2,e.g., if it was not State 1. In the case of an MM-SME coordinated MACentity, the MLME may set the state of the PCP/AP for all MAC entitieswhose address was included in the MMAE parameter of theMLME-ASSOCIATE.request or MLME-REASSOCIATE.request primitive thatestablished the association. The MLME may issue anMLME-DISASSOCIATE.confirm primitive to inform the SME of the successfulcompletion of the disassociation. Upon receiving aMLME-DISASSOCIATE.confirm primitive, the SME may delete any PairwiseTransient Key Security Association (PTKSA) and/or temporal keys held forcommunication with the PCP/AP. In the case of an MM-SME coordinated MACentity, the MLME may perform this operation for all MAC entities whoseaddress was included in the MMAE parameter of the MLME-ASSOCIATE.requestor MLME-REASSOCIATE.request primitive that established the association.

In some demonstrative embodiments, a beamforming link establishedbetween STAs may be used by all MAC sub-layers 153, 154 and 155coordinated by the same MM-SME 146.

In some demonstrative embodiments, if an MMAL cluster capable MAC entityhas successfully transmitted to a peer STA a MMAE, e.g., MMAE 200 (FIG.1), with a BeamLink Cluster field, e.g., field 308 (FIG. 1) set to “1”,then all MAC entities of the STA may use a single, e.g., common,beamformed link for the MMAL cluster. The MAC address used by the STA toinitiate the beamforming procedure may remain the same, for example,until the completion of the beamforming procedure.

In some demonstrative embodiments, a non-MM-SME coordinated MAC entitymay receive an ADDTS request frame from MM-SME coordinated MAC entityincluding an MMAE from the MM-SME coordinated MAC entity. The non-MM-SMEcoordinated MAC entity may include the MMAE of the MM-SME coordinatedMAC entity in an ADDTS Response sent as response. The non-MM-SMEcoordinated MAC entity may not respond with any MMAE, e.g., if thenon-MM-SME coordinated MAC entity is not MMAL cluster capable. The setupof the MMAL Cluster may fail, for example, if the ADDTS response framedoes not contain the MMAE.

In some demonstrative embodiments, a Service Period (SP) may be utilizedby MAC entities of a MMAL cluster. For example, a MAC entity coordinatedby an MM-SME that belongs to an MMAL cluster identified by the SourceAID and Destination AID that are equal to, respectively, the Source AIDand Destination AID of the Allocation field in the Extended Scheduledelement that allocates the SP, may transmit during the SP, if the MACentity sent a MMAE to the peer MAC entity and the BeamLink Cluster fieldwithin the MMAE is set to “1”. A MAC entity coordinated by an MM-SME ofan MMAL cluster identified by the Source AID and Destination AID thatare equal to, respectively, the Source AID and Destination AID of theDynamic Allocation Info field in a Grant frame may transmit during theallocation, if the STA sent a MMAE to the peer MAC entity and theBeamLink cluster field within the MMAE is set to “1”.

Reference is made to FIG. 4, which schematically illustrates a method ofwireless communication, in accordance with some demonstrativeembodiments. In some embodiments, one or more of the operations of themethod of FIG. 4 may be performed by any suitable wireless communicationsystem e.g., system 100 (FIG. 1); wireless communication device, e.g.,devices 102 and/or 130 (FIG. 1); and/or wireless communication unit,e.g., wireless communication units 104 and/or 132 (FIG. 1).

As indicated at block 400, the method may include transmitting awireless communication frame including MMAE corresponding to a pluralityof MAC sub-layers, which share a common physical layer, having arespective plurality of MAC addresses. The MMAE may include two or moreMAC addresses of the plurality of MAC addresses and a control fielddefining at least one common communication attribute to be applied tothe two or more MAC addresses. For example, wireless communication unit104 (FIG. 1) may transmit MMAE 200 (FIG. 2), e.g., as described above.

As indicated at block 402, the method may include establishing a linkbetween the wireless communication unit and a wireless communicationdevice using the MMAE. For example, wireless communication unit 104(FIG. 1) may use MMAE 200 (FIG. 2) for associating with device 130(FIG. 1) and/or establishing at least one wireless communication linkwith device 130 (FIG. 1), e.g., as described above.

As indicated at block 404, the method may include establishing a MMALcluster using the MMAE. For example, wireless communication unit 104(FIG. 1) may establish a MMAL cluster between one or more MAC entitiesof device 102 (FIG. 1) and one or more MAC entities of device 130 (FIG.1), e.g., as described above.

Reference is made to FIG. 5, which schematically illustrates an articleof manufacture 500, in accordance with some demonstrative embodiments.Article 500 may include a machine-readable storage medium 502 to storelogic 504, which may be used, for example, to perform at least part ofthe functionality of wireless communication unit 104 (FIG. 1), wirelesscommunication device 102 (FIG. 1), wireless communication unit 132 (FIG.1), wireless communication device 130 (FIG. 1); and/or to perform one ormore operations of the method of FIG. 4.

In some demonstrative embodiments, article 500 and/or machine-readablestorage medium 502 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 502 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 504 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 504 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features of the invention have been illustrated anddescribed herein, many modifications, substitutions, changes, andequivalents may occur to those skilled in the art. It is, therefore, tobe understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theinvention.

What is claimed is:
 1. An apparatus comprising a memory and a processor,the processor configured to cause a first wireless station (STA) to:transmit a first Multiple Media Access Control (MAC) element to a secondSTA, the first Multiple MAC element comprising a plurality of MACaddresses of MAC entities coordinated by a multiple MAC StationManagement Entity (MM-SME); and based on a second Multiple MAC elementfrom the second STA, set up a Multiple MAC link cluster comprisingMultiple MAC links with the second STA.
 2. The apparatus of claim 1,wherein the first STA comprises anon-Personal-Basic-Service-Set-Control-Point (PCP) or non-Access-Point(AP) (non-PCP/non-AP) STA.
 3. The apparatus of claim 2, wherein thesecond STA comprises a PCP/AP STA, the processor configured to cause thenon-PCP/non-AP STA to transmit to the PCP/AP STA an association requestcomprising the first Multiple MAC element.
 4. The apparatus of claim 3,wherein the second Multiple MAC element is in an association responsefrom the PCP/AP STA.
 5. The apparatus of claim 2, wherein the second STAcomprises a PCP/AP STA, the processor configured to not allow thenon-PCP/non-AP STA to send to the PCP/AP STA an Add Traffic Stream(ADDTS) request with a Transmit Address (TA) field comprising a MACaddress not included in the first Multiple MAC element.
 6. The apparatusof claim 1, wherein the first STA comprises aPersonal-Basic-Service-Set-Control-Point (PCP) or Access-Point (AP)(PCP/AP) STA.
 7. The apparatus of claim 6, wherein the processor isconfigured to cause the PCP/AP STA to transmit to the second STA anassociation response comprising the first Multiple MAC element, inresponse to an association request comprising the second Multiple MACelement.
 8. The apparatus of claim 1, wherein the processor isconfigured to cause the first STA to transmit to the second STA an AddTraffic Stream (ADDTS) request comprising the first Multiple MACelement.
 9. The apparatus of claim 8, wherein the processor isconfigured to cause the first STA to determine that the second STAaccepts the set up of the Multiple MAC link cluster when an ADDTSresponse from the second STA comprises the second Multiple MAC element.10. The apparatus of claim 1, wherein the second Multiple MAC elementcomprises the first Multiple MAC element.
 11. The apparatus of claim 1,wherein the processor is configured to cause the first STA to transmitto the second STA an Add Traffic Stream (ADDTS) response comprising thefirst Multiple MAC element, in response to an ADDTS request from thesecond STA comprising the second Multiple MAC element.
 12. The apparatusof claim 1, wherein the plurality of MAC addresses identify a pluralityof MAC sublayers sharing a common Physical Layer (PHY).
 13. Theapparatus of claim 1 comprising the MM-SME configured to control atleast a power management mode and an antenna configuration of aplurality of coordinated stations (STAs) corresponding to the pluralityof MAC addresses.
 14. The apparatus of claim 1 comprising the MM-SMEconfigured to coordinate management of a plurality of MAC sublayers, aMAC sublayer having a separate MAC Service Access Point (SAP) and aseparate MAC sub-Layer Management Entity (MLME) SAP.
 15. The apparatusof claim 1, wherein the second STA comprises an MM-SME coordinated STA.16. The apparatus of claim 1, wherein the second STA comprises anon-MM-SME coordinated STA.
 17. The apparatus of claim 1 comprising aradio.
 18. The apparatus of claim 1 comprising one or more antennas. 19.An apparatus comprising a memory and a processor, the processorconfigured to cause a first wireless station (STA) to: process a firstMultiple Media Access Control (MAC) element from a second STAcoordinated by a multiple MAC Station Management Entity (MM-SME), theMultiple MAC element comprising a plurality of MAC addresses of aplurality of MAC entities; transmit a second Multiple MAC element to thesecond STA; and set up a Multiple MAC link cluster comprising MultipleMAC links with the second STA.
 20. The apparatus of claim 19, whereinthe first STA comprises a non-MM-SME coordinated STA.
 21. The apparatusof claim 20, wherein the second Multiple MAC element comprises the firstMultiple MAC element.
 22. The apparatus of claim 19, wherein the firstSTA comprises an MM-SME coordinated STA.
 23. The apparatus of claim 19configured to cause the first STA to transmit an Add Traffic Stream(ADDTS) response comprising the second Multiple MAC element in responseto an ADDTS request comprising the first Multiple MAC element from thesecond STA.
 24. The apparatus of claim 23, wherein the second MultipleMAC element comprises the first Multiple MAC element from the secondSTA.
 25. The apparatus of claim 19, wherein the first STA comprises aPersonal-Basic-Service-Set-Control-Point (PCP) or Access-Point (AP)(PCP/AP) STA.
 26. The apparatus of claim 25, wherein the processor isconfigured to cause the PCP/AP STA to transmit to the second STA anassociation response comprising the second Multiple MAC element inresponse to an association request comprising the first Multiple MACelement from the second STA.
 27. The apparatus of claim 26, wherein thePCP/AP STA comprises a non-MM-SME coordinated PCP/AP STA, the secondMultiple MAC element comprising the first Multiple MAC element from thesecond STA.
 28. The apparatus of claim 26, wherein the PCP/AP STAcomprises an MM-SME coordinated PCP/AP STA, the second Multiple MACelement comprising a Multiple MAC element of the MM-SME coordinatedPCP/AP STA.
 29. The apparatus of claim 19, wherein the first STAcomprises a non-Personal-Basic-Service-Set-Control-Point (PCP) ornon-Access-Point (AP) (non-PCP/non-AP) STA.
 30. The apparatus of claim19 comprising a radio.
 31. The apparatus of claim 19 comprising one ormore antennas.